A private network computer uses a client application to request and receive objects from the Internet. Each Catapult Server service can fulfill the requests of a different set of clients.
Catapult Server Proxy service can fulfill requests made by client applications that use any of the following CERN proxy-compatible protocols:
Client applications use protocols compatible with Proxy service include:
Remote Windows Sockets (RWS) can fulfill requests from all Windows Sockets 1.1 compatible applications — applications that support Windows Sockets 1.1. RWS can fulfill requests from clients that use protocols such as:
Clients that use protocols compatible with RWS include:
To learn how to run the Proxy and RWS services together to cache HTTP, FTP, and gopher protocol objects while running all Windows Sockets 1.1 compatible applications, see Chapter 5, “Server Configuration”.
Client Application Settings
The client application is configured through its own user interface. Typically, an application’s relevant settings are found in menu items called “Options”, “Preferences” or “Settings”. You can configure Internet Explorer by using the Internet application in Control Panel.
The Internet application in Control Panel specifies the name of the computer running Catapult Server Proxy service and the protocol port number. You can bypass the proxy when you connect to locations in the Internet application settings. Internet Explorer uses the settings in the Internet application, but other client applications may have their own property sheets or dialog boxes for their proxy service settings.
To configure a computer running a client application to the Proxy service and the protocol port number
Elements of the Internet application are described in the text that follows.
During Catapult Server Setup, a share named Iasclnt is created on the server. This share contains an RWS client Setup program. The RWS client Setup program configures client computers to use the RWS service on that server.
To configure a Remote Windows Sockets client
The RWS client Setup program automatically configures the client computer to use the RWS service (on the server from which RWS client Setup was run). The client computer is configured (not individual applications).
The RWS service supports Windows Sockets version 1.1 applications.
In addition to configuring the client computer to use the RWS service, if the client's Web browser is Microsoft Internet Explorer or Netscape Navigator for Windows NT or Windows 95, client Setup also attempts to configure the browser to use the Proxy service. If this is not appropriate for that client, you may need to reconfigure the client's Web browser after installing the RWS client software.
Note that you can set the client Setup program to only configure clients to use the RWS service, preventing it from configuring browsers to use the Proxy service. To do this, re-run Catapult Server Setup and clear the Set Client setup to configure browser proxy settings option in the Client Access dialog box. Or, you can edit the Iasclnt.ini file and change the Set Browsers to use Proxy=1 parameter to Set Browsers to use Proxy=0. The default location of this file is C:\Ias\Clients.
In a private network with multiple Catapult Server gateways, install RWS evenly from the gateways to the clients to balance Internet traffic across all the gateways. (For information about configuring multiple Catapult Server gateways, see Chapter 5, “Server Configuration.”)
For all client applications, the name of the Catapult Server and the protocol port numbers must be specified either in the Internet application in Control Panel or in the client’s own settings.
Use the Internet application to Configure Internet Explorer to use the Catapult Server Proxy service.
To configure Internet Explorer 2.0 for the Catapult Server Proxy service
Other elements of the Advanced property sheet are described in the text that follows.
Internet Explorer 1.5 is available for Windows NT 3.51 and Windows 3.x clients.x.
To configure Internet Explorer 1.5 for the Catapult Server Proxy Service
Elements of the Proxy dialog box for Internet Explorer 1.5 are described in the text that follows.
Use Netscape™ Navigator 2.01 for Windows NT and for Windows 95 with the Catapult Server Proxy service. In Navigator 2.01, you define the name of the computer running Catapult Server and the port number for each protocol.
To configure Netscape Navigator 2.01 to Proxy service for HTTP protocol requests
For each protocol you use with the Proxy service, you define a Catapult Server name and port number in Navigator’s Proxies property sheet.
Apple® Macintosh® clients can use the RWS service. To configure a Macintosh client application running under UNIX, you need to specify the name of the computer running Proxy service and the Catapult Server port number for the client protocol.
UNIX clients can use the RWS service. To configure a UNIX client application running under UNIX, you need to specify the name of the computer running Proxy service and the Catapult Server port number for the client protocol.
RealAudio is a streaming audio protocol supported by Catapult Server Remote Windows Sockets service. A RealAudio server sends continuous sound over the Internet to RealAudio-compatible clients. The RealAudio Player is a client application that is part of the Catapult Server installation compact disk and is compatible with Internet Explorer.
After installation, RealAudio Player is configured to work with Internet Explorer. Click a Web hyperlink to a RealAudio server to activate the RealAudio Player. You may run RealAudio Player and access RealAudio sites without running Internet Explorer.
To run RealAudio Player, your client computer requires the following:
To configure RealAudio Player for your Catapult Server gateway, use the Network and Proxy property sheets in RealAudio Player.
RealAudio Player Network Properties
RealAudio Player uses Remote Windows Sockets (RWS) to request streaming audio from Internet Sites that run RealAudio Server. RealAudio Player can be configured to work with the User Datagram Protocol (UDP) or Transmission Control Protocol (TCP).
To configure RealAudio Player to receive audio using TCP protocol
Elements of the RealAudio Player Network property sheet are described in the text that follows.
VDOLive Player is provided with Catapult Server.
VDOLive is a streaming video protocol supported by the Catapult Server Remote Windows Sockets service. A VDOLive server sends continuous video image on the Internet to VDOLive compatible clients. VDOLive Player is included as part of the Catapult Server setup.
VDOLive Player runs as a stand-alone application and can be configured to work with Internet Explorer. Select a Web hyperlink to a VDOLive server to activate the VDOLive Player.
To run VDOLive Player, your client computer requires
To configure VDOLive:
© 1996 by Microsoft Corporation. All rights reserved.